URBAN NETWORK INITIATION
1.
ENGAGEMENTS
Figure 1
Document |
Document uploaded |
Date |
* |
|
|
* |
|
|
2.
WORKPLAN Figure 2
SUBMITTED |
APPROVED |
REJECTED |
Insert
Draft work plan template from Collins Approval workflow |
|||
|
|
|
|
|
|
|
|
3.
URBAN
NETWORK ELEMENTS Figure 3
Identification
map description table from Collins Project Manager Acceptance Notification automatically generated
and submitted |
|||
|
|
|
|
|
|
|
|
1. UPLOAD LEGAL DOCUMENTATION Figure
4
Document |
Document uploaded |
Date |
* |
|
|
* |
|
|
Figure 8 Figure 9
MUNICIPALITY FUNCTIONALITY
TABLE (Data)
FIGURE |
FUNCTIONALITY |
WORKFLOW |
BUSINESS RULES |
MILESTONES |
1.
|
Data to be captured into fields and saved to Database
|
None |
Force fields must be completed |
Registration of
Muni |
|
Data to be captured into fields and saved to Database
|
None |
Force fields must be completed |
Registration of
Muni |
3. |
3 x Coordinators details to be
captured into the fields and saved into the database |
None |
Force fields must be completed |
Registration of
Muni |
4.
|
Project manager details to be
captured into the fields and saved into the database |
Project Manager to be notified
on the allocation via e-mail |
Force fields must be completed |
Registration of
Muni |
5. |
Documentation to be uploaded
into the file plan |
Project Manager to be notified
on the upload of legal documentation via e-mail |
Force fields must be completed |
Registration of
Muni |
6. |
Documentation to be uploaded
into the file plan |
Project Manager to be notified
on the upload of financial documentation via e-mail |
Force fields must be completed |
Registration of
Muni |
7.
|
Google map to be provided
indicating the area |
None |
None |
None |
8.
|
Save all data and documentation
captured into the database or file plan. |
Project Manager to be notified
on the registration information complete |
None |
None |
9.
|
Municipality information can be
edited |
Project Manager to be notified
on the registration information edited and saved |
None |
None |